Skip to content

Avoid consulting clock twice between HugePageFiller and TimeSeriesTracker. - #700

Draft
copybara-service[bot] wants to merge 1 commit into
masterfrom
test_978596975
Draft

Avoid consulting clock twice between HugePageFiller and TimeSeriesTracker.#700
copybara-service[bot] wants to merge 1 commit into
masterfrom
test_978596975

Conversation

@copybara-service

@copybara-service copybara-service Bot commented Sep 9, 2026

Copy link
Copy Markdown

Avoid consulting clock twice between HugePageFiller and TimeSeriesTracker.

HugePageFiller::Allocate and HugePageFiller::Put previously queried the cycle
clock multiple times in the same operation (once for lifetime/allocation
tracking and once inside TimeSeriesTracker::Report). Thread the existing
timestamp to SubreleaseStatsTracker::Report and UpdateFillerStatsTracker.

In legacy locking mode (TCMALLOC_INTERNAL_LEGACY_LOCKING), expose now as a dead
parameter and query the cycle clock locally to preserve baseline behavior for
ablation testing.

@copybara-service
copybara-service Bot force-pushed the test_978596975 branch 2 times, most recently from 831000c to a8c80e2 Compare September 9, 2026 21:52
…cker.

HugePageFiller::Allocate and HugePageFiller::Put previously queried the cycle
clock multiple times in the same operation (once for lifetime/allocation
tracking and once inside TimeSeriesTracker::Report). Thread the existing
timestamp to SubreleaseStatsTracker::Report and UpdateFillerStatsTracker.

In legacy locking mode (TCMALLOC_INTERNAL_LEGACY_LOCKING), expose now as a dead
parameter and query the cycle clock locally to preserve baseline behavior for
ablation testing.

PiperOrigin-RevId: 978596975
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant